[DE]Momaw

Did you try just turning off steam input?  Warframe has native support for the PS controller including the correct button icons...

14 hours ago, VladYvhv said:

Still having problems with non-melee incarnons. Phenmore, felarx, laetum, lex prime are ones I commonly use. They still get no incaron recticle when being a client in any sort of mission.

Copied your account, and at least with the active loadout using Lex Prime Incarnon there was no problem. A video of the exact configuration that still has this problem would be helpful.

18 minutes ago, Void2258 said:

What about the general incarnon gun reticles missing for clients?

Is it still a problem after the most recent patch?

We're investigating.  High chance this is related to arcanes equipped on your melee weapon?  If you have an arcane on your melee, try removing it.  If that resolves the problem, come back and let us know 👍

Anybody have images or video? Is this only specific warframes or what? 

1) I equipped Torid Incarnon and Lex Incarnon
2) Joined a fissure mission via matchmaking so I was the client
3) Incarnon charging meter worked fine

Just a small update but very important!

FIXES:

• Fixed a Script Error in text chat that could cause crashing

Just a small update but very important!

FIXES:

• Fixed a Script Error in text chat that could cause crashing

1 hour ago, [DE]Danielle said:

Yes apologies! The team noticed this as well and is working on getting those Clan Trophies sent out :) You should see them soon hopefully!

All done distributing clan trophies!

Warframe has not updated since June, so most likely something going on with your PC rather than the game. 

If you have integrated graphics provided by your CPU,  make sure that Warframe isn't trying to use old integrated graphics instead of your dedicated GPU.  If you click the "Gear" icon in the corner of the launcher,  "GPU Preference" should be "High Performance".

Try running DirectX Diagnostics? That might give some clues.  Start, Run,  "dxdiag" .   Then switch to the "Display" tab, and see what the Name and Manufacturer are (should be Nvidia in your case).  The "Feature Levels" under Drivers, if everything is installed correctly, should show 12_1, 12_0, 11_1, 11_0  etc for an RTX 4070.

Zaky gets the cookie for being the first account we can actually repro the problem on, thanks for the assist.

Now that we have something we can take apart in a debugger, it's under investigation 👍

4 hours ago, Clockwork_The_DragonWolf said:

Its every Time when were NOT the host

So far our testing indicates otherwise 😅

If people really want to help see this fixed, we need to work toward isolating the cause. What is it about the way your start your missions, the way you load, the way you cast abilities, the options you set, SOMETHING, is causing this to happen for you and not for us.  Video would be fantastic, starting all the way back at the Arsenal and then going through Nav and into the mission. And your local Options files might be interesting too, I asked for that earlier.

We deliberately turned off the Aim function on fishing spears in order to stop players from encountering a much more serious problem that could leave you stuck in fishing and unable to continue playing.  Aiming will be restored in the next cert update, when we can deploy the fix for the underlying issue with spears.

The problem is that none of what you're reporting happens at this end. I cloned one of your accounts, switched to Chroma, joined a mission using your loadout (replaced Spectral Scream included), and Elemental Ward was using the correct custom color rather than the default one.  Does this happen EVERY time you play as a client? Or only with specific friends? Or only 10% of the time randomly?

If it's happening every time, then it's not based solely on your loadout. There's some other missing ingredient that you're not aware of and is the real culprit.  It might help us if you can create a new Support ticket, and send us your options files:

• "EE.cfg" from the folder %localappdata%\warframe\
• "Settings" from the folder %localappdata%\warframe\\

The workshops will not be available for stream or VOD, as per the schedule at https://www.warframe.com/tennocon

As some of you already successfully argued, this is not a bug. Arcane Ice Storm is intended to trigger when YOU freeze enemies, and rewards players who invest into building for cold based weapons and cold based abilities.

1 hour ago, Messkoo said:

The description of Frost augment Icy Avalanche is not correct.

The armor bonus is applied only if the enemies have armor.

Not really useful against Corpus or Infested

Can you demonstrate your build? The intent is that the one-time armor scaled bonus is based on YOUR armor, not theirs.  To test, I set up a high strength Frost build with Arcane Guardian, walked up to a Moa, and got over 1000 overguard from Avalanching the single Moa. Same thing with a Charger. 😕

Can confirm that her movement is bound to Character Jump/Crouch rather than the Archwing Move Up/Move Down controls... We did that because she flies like Hildryn (hovering at a fixed altitude over the floor and Up/Down is worldspace relative)  rather than like Titania does (where your altitude is unconstrained and Up/Down is screenspace relative). Would it be more or less confusing to switch the controls? Bearing in mind that if we did that, because of the difference in axes, when you're looking "down" (with relation to enemies on the floor below you)  pressing "forward" would move you "up" and pressing "down" would make you move "forward". We'll consider the change if enough people want it but it might not be for everybody

The mod is intended to be what we call a "stack multiply" effect, and should add together with Point Strike and Vital Sense before multiplying the base weapon stat, which it looks like it currently does, and I can find posts going back as far as 2022 when we introduced the mod supporting this. It looks like the only thing that's changed in this recently was done to avoid double-dipping the extra +100% critical multiplier that Frozen targets now innately provide with the Jade status overhaul, but that shouldn't affect the critical chance. If you were previously seeing weapons go from normal hits to constant red crits due to Biting Frost forcing a floor of 300% on critical chance, I don't know what to say other than that was the bug because that's not what it was intended by the designer to do.

With Visual Effect Intensity at 100% (default)  and with Bloom turned down to a conservative 12%, the pickups are fairly visible here? I suspect it's some other graphical setting that's causing problems....

Biting Frost seems to work okay here. We'll need more precise steps to follow, if this is still an ongoing problem. Try reproducing solo, and with the minimum amount of mods/upgrades possible. We also love videos!